From: Florian Müllner Date: Thu, 13 Feb 2020 22:16:38 +0000 (+0100) Subject: unlockDialog: Use "normal" background X-Git-Tag: archive/raspbian/50.5-1+rpi1~1^2~772^2^2~71 X-Git-Url: https://dgit.raspbian.org/%22http://www.example.com/cgi/%22/%22http:/www.example.com/cgi/%22?a=commitdiff_plain;h=0afac367135d3e1a6eef3c86c6e7f1dcfc339ece;p=gnome-shell.git unlockDialog: Use "normal" background Now that we apply a strong blur effect to the background, it doesn't make too much sense to use a separate lock-screen background: It will be mostly unrecognizable anyway. The alternative would be to turn off the blur effect if a different background is used (or have a hidden setting for that), but that would then imply that we must keep the contents readable without blur. Let's avoid that rabbit hole and just re-use the regular background. https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/1001 --- diff --git a/js/ui/unlockDialog.js b/js/ui/unlockDialog.js index 7f33e68e1..5a3d24fd2 100644 --- a/js/ui/unlockDialog.js +++ b/js/ui/unlockDialog.js @@ -18,8 +18,6 @@ const IDLE_TIMEOUT = 2 * 60; // The timeout before showing the unlock hint (in seconds) const HINT_TIMEOUT = 4; -const SCREENSAVER_SCHEMA = 'org.gnome.desktop.screensaver'; - const CROSSFADE_TIME = 300; const FADE_OUT_TRANSLATION = 200; const FADE_OUT_SCALE = 0.3; @@ -624,7 +622,6 @@ var UnlockDialog = GObject.registerClass({ container: widget, monitorIndex, controlPosition: false, - settingsSchema: SCREENSAVER_SCHEMA, }); this._bgManagers.push(bgManager);